I've pulled your PR and tested, it doesn't seem to account for smaller window width, which will lead to some images being cut off or invisible to the user (in some cases where window width is perfectly cutting off an image)

I've also spoken the to UX/UI team and the general feedback was that this makes the app feel more cluttered, so i think we would err on the side of closing this unless there is significant community desire for this change.

unless there is significant community desire for this change

Here to voice community desire.

I've pulled your PR and tested, it doesn't seem to account for smaller window width, which will lead to some images being cut off or invisible to the user (in some cases where window width is perfectly cutting off an image)

This PR was born of the failure of Session to account for large window sizes when displaying multiple attachments.

If you feel that this change doesn't take into account narrower window sizes, then I think we're coming to an important realisation: Neither of us knows how wide the user's Session window is, and different users will have windows of different widths. Why should any of them have to compromise?

Perhaps the best behaviour, then, is one that adapts to the amount of horizontal space available to each and every user. The more space available, the greater the number of attachments that can be shown without cluttering the screen.

Closing for now, as this PR does not account for window size, there doesn't seem to be significant community desire and the UX/UI team has expressed their view that increasing the default images shown makes the application feel more cluttered, which they would like to avoid.

UI/UX decisions like this are always going to be feel fairly arbitrary, akin to judging art, its in the eye of the beholder; which designs enhance function while preserving form? so i can understand feeling annoyed. Nonetheless thank you for putting in the effort to produce this code and submit this PR.

there doesn't seem to be significant community desire

Go ask in the image focused communities about that. The people who would support that cause are simply not aware of it, because they aren't active on GitHub.

Closing for now, as this PR does not account for window size, there doesn't seem to be significant community desire and the UX/UI team has expressed their view that increasing the default images shown makes the application feel more cluttered, which they would like to avoid.

the fact that he made this PR is proof that there is a very notable non trivial amount of community desire.

this needs to be reopened and our process in how we do UI/UX revised to include the community as the primary entity involved.